You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(cli): pin @relayflows/sdk 2.0.66 so 18.0.0 installs beside it - #2127
The 18.0.0 publish (run 42576272570) failed in Build & Version. relayflows-peer-compat.test.ts hit ERESOLVE because @relayflows/sdk@2.0.65's optional @agent-relay/sdk peer stops at <18. Nothing was published.
flows #709 widened that peer to <19, and it's published as @relayflows/sdk 2.0.66. #709 is the only flows change since 2.0.65.
Change
Pins @relayflows/sdk 2.0.66 in package.json, packages/cli/package.json and the product-surfaces.ts range.
Updates the exact version that the GitLab released-pins case checks.
Lockfile: only the two @relayflows entries and the two pin lines change.
A full npm install --package-lock-only also moved @agent-relay/sdk off its workspace link to a registry copy under packages/cli, and marked packages/sdk extraneous.
That doesn't happen on untouched main, so I kept those entries as they are on main, the same as the Relay 17 pin (5a9f0b7).
No changelog entry: this only unblocks the release.
The root overrides entry stays unchanged; the publish workflow rewrites it during the version bump.
Validation
Lockfile: integrity hashes match the registry for @relayflows/sdk and @relayflows/surface 2.0.66. npm ci accepts the lockfile, and npm ls shows @agent-relay/sdk linked to ./packages/sdk.
Peer-compat test:relayflows-peer-compat.test.ts passes at 17.2.1, and again with the CLI version set to 18.0.0, which is the case that failed the release.
Typecheck:npm run typecheck passes.
Full suite: I couldn't complete it locally because the disk filled up (ENOSPC), so CI is the full-suite check.
After merge
Rerun the 18.0.0 publish (package=all, version=major).
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.
The 18.0.0 publish (run 42576272570) failed the peer-compat release test
with ERESOLVE: @relayflows/sdk 2.0.65's optional @agent-relay/sdk peer
stops at <18. 2.0.66 (flows #709) accepts <19 and is otherwise 2.0.65.
The pin moves in package.json, packages/cli/package.json, the
product-surfaces range and the GitLab released-pins case. The lockfile
changes only the @relayflows/sdk and nested @relayflows/surface entries
and the two pin lines. A full regeneration also moved @agent-relay/sdk
off its workspace link to a registry copy under packages/cli, so those
entries are kept as on main, as for the Relay 17 pin (5a9f0b7).
Validation: integrity hashes match the registry; npm ci accepts the
lockfile and links @agent-relay/sdk to ./packages/sdk;
relayflows-peer-compat.test.ts passes at 17.2.1 and with the CLI
version set to 18.0.0; npm run typecheck passes. The full vitest run
here hit ENOSPC (disk full), so CI is the full-suite check.
Co-authored-by: Cursor <cursoragent@cursor.com>
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.
No actionable comments were generated in the recent review.
Walkthrough
The root and CLI manifests, standalone provisioning pin, and GitLab released-product proof now use @relayflows/sdk version 2.0.66 instead of 2.0.65. The product-surface comment updates the supported Relay range to 15.1–18.
Changes: Flows SDK version update
Layer / File(s)
Summary
Update SDK pin and proof package.json, packages/cli/package.json, packages/cli/src/cli/commands/product-surfaces.ts, tests/relayflows/cases/gitlab-released-product-pins/run.mjs
The manifests and standalone provisioning pin now use @relayflows/sdk version 2.0.66. The product-surface comment names Relay peer support through version 18. The released-product proof expects SDK version 2.0.66.
AgentWorkforce/relay#2084: Updates the same Relayflows SDK pins in connection with peer compatibility.
AgentWorkforce/relay#2078: Updates the same SDK dependency pins and tests compatibility with published peer ranges.
AgentWorkforce/relay#2089: Updates the SDK dependency and product-surface pins, and checks the pinned version in the released-product proof.
Merge Risk: Minimal · up to 7be1c
This updates a pinned SDK dependency so the 18.0.0 publish can proceed. The supplied diffs show no behavior change and no remaining merge-blocking risk.
Pre-merge checks: 5
Check name
Status
Explanation
Title check
The title clearly identifies the SDK version pin and its purpose: allowing Relay 18.0.0 to install alongside it.
Description check
The description explains the reason for the change, lists the updates, and reports validation results. It does not use the template’s Summary, Test Plan, or Screenshots headings, but it provides the r…
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Description check
Explanation
The description explains the reason for the change, lists the updates, and reports validation results. It does not use the template’s Summary, Test Plan, or Screenshots headings, but it provides the required summary and test information; screenshots are not applicable.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 2 files.
Finishing Touches
Generate docstrings
Commit to this branch
Create a new PR
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Some tools did not complete. Review the errors below.
ESLint
If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.
ESLint install timed out. The project may have too many dependencies for the sandbox.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
A rabbit checks the version line, Two point oh six six looks fine. The pins align from root to CLI, The proof now checks the same nearby. Relay eighteen joins the range, A tidy hop, a small release change.
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: CHILL
Plan: Advanced
Run ID: 9db572f3-1d08-46c8-82b5-9ceffff56861
Commits
Reviewing files that changed from the base of the PR and between c6253d9 and 7be1c37.
Files selected for processing: 1
packages/cli/src/cli/commands/product-surfaces.ts
Files skipped from review as they are similar to previous changes: 1
packages/cli/src/cli/commands/product-surfaces.ts
Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.
The reason will be displayed to describe this comment to others. Learn more.
One small but release-facing correction before approval: packages/cli/src/cli/commands/product-surfaces.ts still says the pinned Flows SDK has support for “Relay 15.1 through 17 peers.” This PR exists because 2.0.66 extends that peer contract through Relay 18, so the adjacent comment is now false. Please update it to “through 18” (or equivalent), rerun the focused checks, and request review on the exact successor head. The manifest/lock changes and registry integrities otherwise match the published 2.0.66 artifacts.
The reason will be displayed to describe this comment to others. Learn more.
Approved exact successor head 7be1c37. The Relay-18 comment is corrected, the only changed artifacts remain the exact 2.0.66 pins/lock metadata/proof expectation, and both registry integrity values match npm. No unresolved threads. Merge after the refreshed required checks are terminal green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
AgentRelayBot
left a comment
Why
The 18.0.0 publish (run 42576272570) failed in Build & Version.
relayflows-peer-compat.test.tshit ERESOLVE because@relayflows/sdk@2.0.65's optional@agent-relay/sdkpeer stops at<18. Nothing was published.flows #709 widened that peer to
<19, and it's published as@relayflows/sdk2.0.66. #709 is the only flows change since 2.0.65.Change
@relayflows/sdk2.0.66 inpackage.json,packages/cli/package.jsonand theproduct-surfaces.tsrange.@relayflowsentries and the two pin lines change.npm install --package-lock-onlyalso moved@agent-relay/sdkoff its workspace link to a registry copy underpackages/cli, and markedpackages/sdkextraneous.main, so I kept those entries as they are onmain, the same as the Relay 17 pin (5a9f0b7).overridesentry stays unchanged; the publish workflow rewrites it during the version bump.Validation
@relayflows/sdkand@relayflows/surface2.0.66.npm ciaccepts the lockfile, andnpm lsshows@agent-relay/sdklinked to./packages/sdk.relayflows-peer-compat.test.tspasses at 17.2.1, and again with the CLI version set to 18.0.0, which is the case that failed the release.npm run typecheckpasses.After merge
Rerun the 18.0.0 publish (
package=all,version=major).Open in [code]smith · Need help on this PR? Tag
@codesmith-botwith what you need.